Draft
Conversation
e694de0 to
6950f57
Compare
4018e12 to
06793ef
Compare
06793ef to
b86f01b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Problem
the current method for getting changes shipped takes a lot of clicks, and at least 3 separate modals -- create branch, commit, create PR.
for what i expect to be the more general case ("agent did work, i wanna ship it"), we can simplify this
removed
added
introduces a new unified "create PR" workflow that does these steps, as needed:
create pr flow notes:
minor fixes along the way
How did you test this?
i have not yet tested this in cloud or worktrees
manually tested, i know it's a big PR, so would appreciate others manually testing a bit too 💪